home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
User's Choice Windows CD
/
User's Choice Windows CD (CMS Software)(1993).iso
/
win_a_d
/
31updt.zip
/
README
< prev
next >
Wrap
Text File
|
1991-09-01
|
4KB
|
115 lines
Welcome to Borland C++ and the Windows 3.1 SDK
----------------------------------------------
Using Borland C++ 2.0 to create Windows 3.1 applications is fairly easy.
Only minor changes to windows.h and a new import.lib file are needed. This
diskette contains an archive file called 31UPDATE.ZIP that contains in it new
versions of several header files included with Borland C++ 2.0 as well as a
new version of import.lib. The README file describes the installation process
and any other changes necessary which allow Borland C++ 2.0 to create
Windows 3.1 applications. Please read this file in its entirety.
TABLE OF CONTENTS
-----------------
1. How to Get Help
2. Installation
3. MakeProcInstance and FreeProcInstance
4. Using Import Libraries
5. Using Turbo Debugger for Windows
6. Important Information
1. HOW TO GET HELP
-------------------
If you have a question and need assistance, help is available from the
following sources:
1. Type GO BPROGB on the CompuServe bulletin board system for
instant access to the Borland forums with their libraries of
technical information and answers to common questions.
If you are not a member of CompuServe, see the enclosed
special offer, and write for full details on how to receive
a free IntroPak containing a $15 credit toward your first
month's on-line charges.
2. Check with your local software dealer or users' group.
3. If you have an urgent problem that cannot wait and you have
sent in the license agreement that came with the package,
you may call the Borland Technical Support Department at
(408) 438-5300. Please have the following information ready
before calling:
a. Product version number. The version number for Borland
C++ can be displayed by pressing Alt-Space/A.
b. Computer brand, model, and the brands and model numbers of
any additional hardware.
c. Operating system and version number. (The version number
can be determined by typing VER at the MSDOS prompt.)
d. Contents of your AUTOEXEC.BAT file.
e. Contents of your CONFIG.SYS file.
2. INSTALLATION
----------------
To install the files included on this diskette copy 31UPDATE.ZIP from
the floppy diskette into the BORLANDC\BIN directory on your local
hard disk.
Once you have copied the archive file included within to your hard
disk execute the following commands.
unzip /o 31update.zip *.h ..\include
unzip /o 31update.zip *.lib ..\lib
The unzip utility will unpack the file contained in 31UPDATE.ZIP and
place them in the directory specified on the command line. Once this
file has been dearchived you will have installed new versions of the
header files used in a Windows application as well as a new import.lib.
3. MAKEPROCINSTANCE AND FREEPROCINSTANCE
----------------------------------------
A change MUST be made to several sample applications included in the
Windows 3.1 SDK when a call to MakeProcInstance or FreeProcInstance exists.
A cast to FARPROC needs to be inserted in front of the function name being
passed to either MakeProcInstance or FreeProcInstance. Below is an example
of what the change needed is:
Old code:
lpProcAbout = MakeProcInstance(About, hInst);
New code:
lpProcAbout = MakeProcInstance((FARPROC) About, hInst);
4. USING IMPORT LIBRARIES
-------------------------
All import libraries included with the Windows 3.1 SDK, with the exception of
libw.lib, can be used directly with Borland C++ 2.0 without any changes or
modifications.
Libw.lib is replaced with a new version of IMPORT.LIB that can be found in
the archive file 31UPDATE.ZIP.
5. USING TURBO DEBUGGER FOR WINDOWS
-----------------------------------
In order to user Turbo Debugger with Windows 3.1 you need only replace the
file windebug.dll shipped with Borland C++ 2.0 with the one included in the
Windows 3.1 SDK. Remember to save the existing version of windebug.dll for
future use.
6. IMPORTANT INFORMATION
------------------------
Please note that additional changes to specific header files shipped with
the Windows 3.1 SDK may be necessary in order to compile the example programs
included with the new SDK.